System and methods for integrated multistreaming of media with graphical overlays

ABSTRACT

This present disclosure describes a system and methods for integrated multistreaming of media with graphical overlays. At least one method includes a multistream service and graphical overlays hosted by a server infrastructure; a user configuring both the multistream service and graphical overlays on the server infrastructure; a user playing video games on a computer, using broadcasting software to authenticate with the server infrastructure; the broadcasting software capturing video of the user&#39;s computer session; the software retrieving the user&#39;s custom graphical overlay from the server infrastructure, encoding the video signal and graphical overlay; the software using the same aforementioned authentication to upload the encoded video to a multistream service, and the multistream service streaming the user&#39;s encoded video simultaneously to multiple streaming services.

FIELD OF THE DISCLOSURE The present disclosure relates to providingdifferent streaming services with video content including videooverlays. BACKGROUND

This present disclosure relates to a system and methods for integratedmultistreaming of media with graphical overlays.

The online video industry has grown rapidly since YouTube made it simpleto share online videos in 2005. Netflix introduced its streaming videoservice in 2007, followed by Hulu in 2008. All three services focused onpre-recorded video, also known as Video On Demand (“VOD”), until YouTubeintroduced YouTube Live in 2008. It marked the first easily accessibleimplementation of a live streaming video service.

Similarly, video games have evolved from single or multiplayerexperiences shared around a single TV to complicated, internet-basedmultiplayer games that allow hundreds of thousands of players toparticipate in shared gaming experiences. Fans of video gameshistorically used magazines such as GamePro Magazine to stay abreast ofnew game releases, uncover otherwise difficult to find game secrets, andto learn how optimize their gameplay. Eventually the medium was replacedby YouTube channels dedicated to video game content.

The popularity of online video game content lead to the founding of anew class of Streaming Services: Twitch, which was founded in 2011, andYouTube Gaming which came online in 2015. These services allowed playersto directly broadcast their own gaming experiences to the world.Streaming Services differ from the aforementioned Netflix, Hulu, andYouTube products in that they focus on streaming live video, as opposedto pre-recorded VOD content. Today Twitch serves over 170 millionvisitors every month, and unlike YouTube's VOD product, which primarilyserves short-form video, the average Twitch visitor views over an hourof streaming content. For the purpose of the present invention, the termStreaming Services refers to one or more services designed to streamlive video content via a digital channel including, but not limited to,Twitch, YouTube Gaming, Mixer, and Facebook Live.

These extended viewing times are enabled by video game fans' voraciousappetite for video game content, and by Streaming Services such asTwitch or YouTube Gaming providing tools to enable users broadcastingtheir games, the Streamers, to monetize the time they spend streamingtheir game sessions. These tools include allowing Viewers to sign up fora monthly subscription to the channel of a specific Streamers whosepersonality or gameplay they enjoy, a chat panel for Viewers to chatwith each other and the Streamer, and an extensive applicationprogramming interface (API) for developers to build applications thatinterface with the Streaming Services. Many Streamers are able to make asubstantial living through Streaming Services and the ecosystems theyhave created.

Due to the instantaneous and live nature of video streamed to StreamingServices, it is not possible to edit a video before it goes live usingtraditional video editing software. To overcome this limitationbroadcasting software, such as Open Broadcaster Software (“OBS”), hasintroduced the ability to use Overlays, which are graphical elementsthat are added to the Streamer's video immediately prior to the videobeing encoded and sent to Streaming Services for Viewer consumption.Overlays can consist of static or dynamic images, and they can be storedlocally or hosted on a server.

Furthermore, Streaming Services and Streaming Service APIs have enabledan ecosystem of third-party tools that help Streamers monetize theirchannels beyond Viewer subscriptions. Key features developed bythird-party services include facilitating donations (a primary source ofincome for Streamers). Multistream Services that broadcast a singleStreamers video feed to multiple simultaneous Streaming Services, chatbots that help Streamers engage with and manage their Viewers throughthe chat pane, and custom Overlays. Said custom Overlays can providestatic images, such as decorative video borders, animated graphics thatrespond in real time to the actions of the Viewers or the game.

An example of a real-time alert includes an animated alert appearing inthe Streamer's video feed when a Viewer subscribes, follows, or donatesto the Streamer. This allows the Streamer to easily see Viewermonetization events as they occur. It also gives the Viewer a chance atnotoriety as their name is displayed in front of potentially millions ofother Viewers.

Another example of a real-time alert is a widget system that allows theStreamer to display the chat pane contents directly within the videofeed. This allows the Streamer to monitor both the output of their livestream and their Viewer conversations in one place, without having tomanually show and hide the chat panel while they are live. These andother alert examples have become integral to the success of StreamingServices, and Viewers have come to expect them from their favoriteStreamers.

Streamers may also need to broadcast their signal to multiple platformsin order to increase the amount of Viewers reached and the subsequentlyrevenue the streamer is able to generate while streaming. As of thewriting of this patent, a number of inventions have been introduced thataddress this need. Multistream services such as Restream.io orSwitchboard live provide access to multistreaming infrastructure forStreamers. Access to Multistream Services was heretofore made possibleby manually configuring broadcasting software, such as OBS, to send theStreamer's video to said third-party Multistream Service. To begin usingthe Multistream Service, a Streamer is required to sign up for anaccount with a Multistream Service provider, then follow instructionsfrom the provider to generate and manually transfer their credentialsfor the stream to the broadcasting software, where said credentials areoften an API key that associates the signal with the user's account inthe Multistream Service; the broadcasting software then uploads thestream along with the user's API key to the third-party MultistreamService, which then redirects your stream to multiple StreamingServices. A Streamer could alternatively build their own custommultistreaming server. Note that either solution is in addition tocreating an account with the service that generates the GraphicalOverlay, which must also generate a custom URL for the user's GraphicalOverlay, which must then be manually added to the broadcasting software.

While both approaches functionally work, they require considerabletechnical know-how, they add extra steps to the process of setting up astream, thus increasing the number of Streamers who are unable tocomplete the setup process, or they fail to provide the Streamer withthe unique benefits granted by integrating said services. Additionally,because the Server Infrastructure is separated from the MultistreamService, Streamers are limited to using the same Graphical Overlay foreach Streaming Service to which they broadcast. While a single overlaymight have worked well in the past, Viewers on different StreamingServices may care about different aspects of the stream, and they mayonly care to be alerted to subscription, follow, and donation eventsrelated to the Streaming Service they are currently watching as thosenotifications often allow them to interact with like-minded Viewers whohave also chosen to support their favorite Streamer. Furthermore, it isnot possible for a Streamer to conveniently manage both the multistreamservice connections and their graphical overlays in a single serverinfrastructure. These are just some of the many reasons a Streamer'saudience is better served by graphical overlays that are customizable toeach Streaming Service.

SUMMARY

Presently disclosed is a system and methods for integratedmultistreaming of media with graphical overlays. In embodiments, themethod includes a server infrastructure configured to host a user'scustom video overlay on the server infrastructure, said overlayconfigured to incorporate graphics and/or audio and overlayconfiguration information for a given video overlay, where saidconfiguration information specifies values for one or more settings thatdefine the application of the image and/or audio of the given videooverlay; the user configuring said overlay with text and/or graphics;the server infrastructure configured to receive data from a data API;the graphics configured by the user to respond to one or more predefinedAPI data events; the user saving the overlay configuration to the serverinfrastructure; server infrastructure producing an image file inresponse to the predefined API data events as specified in the overlayconfiguration; the server infrastructure configured to establishcommunication with one or more streaming services, wherein the streamingservices are configured to receive and transmit information; serverinfrastructure configured to receive from the one or more streamingservices API data events generated by viewer input informationassociated with another user's interaction with the different streamingservices; the server infrastructure configured to connect the user'saccount to the one or more streaming services; the user configuring saidstreaming service connections on configuration pages presented by theserver infrastructure or via settings in the local broadcast software,which would then submit the configurations to the server infrastructure;the server infrastructure being configured to store the user's streamingservice connection configuration; the user authenticating to the serverinfrastructure using local broadcasting software; the broadcastingsoftware retrieving the overlay image from the server; the localbroadcasting software encoding video output from the user's computer andthe overlay image to produce a video file; the local broadcastingsoftware connecting to a multistream service based on the user'spreviously-granted authentication to the server infrastructure; thelocal broadcasting software uploading the encoded video file to themultistream service, which is configured to upload the encoded videofile to one or more streaming services as determined in the user'smultistream configuration; the streaming service decoding the videofile; the streaming service displaying the video for consumption by aplurality of users.

In some embodiments, the local broadcasting software is configured toallow a user to directly connect to multiple streaming services.

In some embodiments, the local broadcast software is configured to allowa user to authenticate to the server infrastructure hosting thegraphical overlay in addition to authenticating with a separatemultistream service; while an API key simply identifies an account to amultistream service, authentication often includes, yet not limited to,providing a username and password for full access to the user account.

In some embodiments, the independent streaming services are hosted ondifferent servers.

In some embodiments, the user connects a multistream service to theiraccount hosted by the server infrastructure in place of or in additionto connecting independent streaming services.

In some embodiments, the broadcasting software encodes the output of theuser's local webcam with the overlay and the video feed.

In some embodiments, the broadcasting software is operated from aself-contained mobile computer, including, but not limited to asmartphone, augmented or virtual reality equipment.

In some embodiments, the broadcasting software combines media outputsfrom multiple computers to produce the encoded video file.

In some embodiments, the API data is received from multiple data APIsources.

In some embodiments, some or all API data is received from a programoperating on the User's local computer, such as the user's video gameprogram.

In some embodiments, the overlay configuration specifies the position,duration, and/or real-time event trigger for determining when the imageand/or audio of the given video overlay is applied.

In some embodiments, the video content includes an image of the user'sface, wherein the image of the given video overlay is positionedrelative to the user's face based on the one or more settings thatdefine the application of the image and/or audio of the given videooverlay to the video content.

In some embodiments, some or all API data is received from a computervision program or artificial intelligence engine operating on the User scomputer.

In some embodiments, some or all API data is received from a computervision program or artificial intelligence engine operating in the serverinfrastructure.

In some embodiments, some or all API data is received from a computervision program or artificial intelligence engine operating in themultistream service.

In some embodiments, the multistream service decodes the encoded videofile, then encodes the video in formats suitable to one or morestreaming services, then uploads the encoded outputs to eachcorresponding streaming service, the streaming services then decode thevideo file and display the video for consumption by a plurality ofusers.

In some embodiments, API data is received from multiple data APIsources; one or more data sources are designated to create graphicsspecific to one or more video streaming services: said graphics are usedto create one or more overlay; the encoded output of the video and eachoverlay are then uploaded by the local broadcasting software to amultistream service, which uploads one or more corresponding encodedoutputs to one or more corresponding streaming service.

Also disclosed is a system and methods for integrated multistreaming ofmedia with graphical overlays that includes a server infrastructureconfigured to host a user's custom video overlays on the serverinfrastructure, said overlays configured to correspond to one or morestreaming service; the user configuring said overlays with text and/orgraphics and/or audio and overlay configuration information for a givenvideo overlay, where said configuration information specifies values forone or more settings that define the application of the image and/oraudio of the given video overlay; the server infrastructure configuredto receive data from one or more data API(s); the graphics configured bythe user to generate based on one or more predefined API data eventscorresponding to one or more streaming services; the user saving theoverlay configurations to the server infrastructure, where each overlayconfiguration corresponds to one or more streaming service; serverinfrastructure producing one or more image file(s) in response to thepredefined API data events as specified in the overlay configuration;the server infrastructure configured to establish communication with oneor more streaming services, wherein the streaming services areconfigured to receive and transmit information; server infrastructureconfigured to receive from the one or more streaming services API dataevents generated by viewer input information associated with anotheruser's interaction with the different streaming services; the serverinfrastructure configured to connect the user's account to the one ormore streaming services; the user configuring said streaming serviceconnections on configuration pages presented by the serverinfrastructure or via settings in the local broadcast software, whichwould then submit the configurations to the server infrastructure; theserver infrastructure being configured to store the user's streamingservice connection configuration; the user authenticating to the serverinfrastructure using local broadcasting software; the local broadcastingsoftware encoding video output from the user's computer to produce avideo file; the local broadcasting software connecting to a multistreamservice based on the user's previously-granted authentication to theserver infrastructure; the local broadcasting software uploading theencoded video file to the multistream service; the multistream serviceretrieving the user's one or more overlay image file(s); the multistreamservice decoding the encoded video file, then re-encoding a copy of thevideo file for each retrieved overlay image file(s); the multistreamservice uploading the re-encoded video file(s) to the correct streamingservices based on the graphical overlay included in the video file ormetadata correlating the completed video file to its associatedstreaming service; the streaming service decoding the video file; thestreaming service displaying the video for consumption by a plurality ofusers.

In some embodiments, the generated graphics are customized by the userto be unique to one or more streaming service(s).

In some embodiments, the generated graphics are variants provided by theserver infrastructure.

In some embodiments, the overlay configuration specifies the position,duration, and/or real-time event trigger for determining when the imageand/or audio of the given video overlay is applied.

BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding of the various disclosed embodiments can beobtained when the following detailed description is considered inconjunction with the attached drawings, in which:

FIGS. 1A and 1B shows a system diagram that includes an illustrative WebInfrastructure with multiple data sources and multistreaminfrastructure.

FIG. 2 shows a software flowchart of a system for configuring amultimedia overlay.

FIG. 3 shows a non-limiting example of a configured multimedia overlay.

FIG. 4 shows a software flowchart of a user connecting their account tostreaming services.

FIGS. 5A and 5B shows a software flowchart and functional distributionfor a first illustrative embodiment.

FIGS. 6A and 6B shows a software flowchart and functional distributionfor a second illustrative embodiment.

It should be understood that the drawings and corresponding detaileddescription do not limit the disclosure, but on the contrary, theyprovide the foundation for understanding all modifications, equivalents,and alternatives falling within the scope of the appended claims.

DETAILED DESCRIPTION Introduction

The disclosed embodiments relate to multistreaming media with graphicaloverlays for use with video games, movies, entertainment media and/orother non-entertainment media. More specifically, the disclosedembodiments relate to interconnected systems executing software relatedto local software sending an encoded user signal anddynamically-generated, web-hosted graphical overlay to a serviceconfigured to upload videos to one or more streaming services.

The disclosed embodiments rely on a live video streaming architecture,where part of the stream includes inserting a graphical over lay priorto encoding the video for distribution. The user in these embodiments(e.g. the “streamer”) configures the graphics that will be generatedinto a video overlay in real time based on data received from API datasources. The user then connects one or more third-party streamingservice to their account, which is stored in the server infrastructureand accessed via the multistream service. The user then authenticates tothe server infrastructure through their local broadcast software, whichallows the local broadcast software to access services hosted by theserver infrastructure such as the users generated overlay image and theaforementioned multistream service. The user then configures localbroadcast software to combine two or more separate data sources into anencoded video: a specific application or video game signal; theinternet-hosted video overlay, which is generated by the serverinfrastructure at regular intervals to give the appearance that it isanimated and synchronized to current events in the application or videogame signal; and optionally the user's local camera feed, which, whenincluded, may allow viewers to see the user as they are using theirapplication or playing a video game. The aforementioned signals are thenencoded by the local broadcast software for upload to the multistreamservice; (because the user has already authenticated to the serverinfrastructure, which contains the multistream service, the localbroadcast software already has access to the user's connections in themultistream service;) the multistream service then uploads the encodedvideo to one or more third-party streaming websites, such as Twitch,YouTube Gaming, Mixer, or Facebook Live, based on the user's previouslydefined connections to said streaming services.

Given that multistream systems and graphical overlays are integral tothe monetization of a streamer's channel, and given that streamerstypically only receive donations and subscriptions while they arestreaming, it is in their best interest to minimize the time they spendmanaging and customizing the disparate systems required to produce asuccessful live stream.

In contrast to prior systems, a system for integrated multistreaming ofmedia with graphics makes it seamless for streamers to configure andmanage the critical services that comprise their live streams. While anAPI key allows a multistream service to associate a video with thecorrect user account, it is not a complete form of authentication, thusdoes usually not provide sufficient account security to permit thetransfer of stored user preferences between a multistream service and alocal broadcast software. Fully authenticating with the serverinfrastructure, often via a username and password, instead of simplysending an API key provides for tighter integration between the serverinfrastructure and the local broadcast software. This tighterintegration allows the server infrastructure to provide the localbroadcast software with access to data user preferences, such as thegraphical overlay and multistream service configurations; it also allowsthe local broadcast software to display details from the user's accountthat would typically only be accessible within the serverinfrastructure, such as information received by the third-partystreaming service data APIs related to the user's connection accounts.

Additionally, by allowing a user to fully authenticate their localbroadcast software to a server infrastructure that provides access toboth the multistream service and the user's graphical overlays, thedisclosed embodiments provide a simple setup experience that iscurrently unrivaled in the consumer broadcasting market. Not unlikeAmazon's one-click checkout invention, this consolidated setup providesa significant competitive advantage to the company that provides theservice and the streamers who utilize it.

The paragraphs that follow describe in detail various examples of theabove-described embodiments. An example of an illustrative Webinfrastructure utilizing dynamic data and multi-streaminginfrastructure. The individual use-cases that complete the system (i.e.,an individual establishing connections to third-party streaming servicesand using images to configure an overlay) are then described throughsoftware flowcharts. A non-limiting illustrative example of a configuredoverlay is then provided. Finally two illustrative embodiments aredescribed, wherein the graphical overlay is encoded by the localbroadcast software then sent to the multistream service, and thegraphical overlay is added to the video after it is received by themultistream service.

Web Infrastructure With Multiple Data Sources and MultistreamInfrastructure

FIGS. 1A and 1B shows an overview of an illustrative embodiment of a webinfrastructure with multiple data sources and multistream infrastructurethat includes the Server Infrastructure 100, an Internet 120infrastructure, a Local Computer 230 operating Local Broadcast Software240, a Multistream Service 250, a Streaming Service 150, Viewers 170, amethod for collecting Viewer Interactions 160, and one or more StreamingService API(s) 130. The Server Infrastructure 100 contains a method forpersistent storage, such as a database, as well as a method forinitiating and responding to internet requests, such as a web server.The Server Infrastructure 100 stores and makes various user settingsavailable for retrieval, including the user's Overlay Configuration 110and the user's Graphical Overlay 200. This embodiment potentiallyincludes Alternative API Data Sources 270 which are data sourcesunrelated to the Streaming Service API(s) 130 that are used in thecreation of the Graphical Overlay 200. This embodiment of the ServerInfrastructure 100 contains the Multistream Service 250, which storesand maintains the user's connections to third-party Streaming Services150. This embodiment of the Server Infrastructure 100 also contains anAPI Data Collector 260, which is responsible for aggregating data fromone or more Streaming Service API(s) 130 and Alternative API DataSources 270. Data gathered by the API Data Collector 260 is then used incombination with the user's Overlay Configuration 110 to populate theGraphical Overlay 200. While not depicted in this embodiment, theAlternative API Data Sources 270 may also be generated by a localprogram executing on the user's computer.

The Local Computer 230 may be a traditional desktop computer, a laptop,a mobile phone, a virtual or augmented reality computing device, or anyrelated personal computing device. The Streaming Service API(s) 130 andthe Alternative API Data Sources 270 connection(s) may be unidirectionalor bilateral. The Streaming Service API(s) 130 and the Alternative APIData Sources 270 may also be a RESTful service, a persistent websocketsconnection, or any other method of regularly publishing and sharinginformation between disparate internet systems. The Game Signal 220includes, but is not limited to, an audio/video signal from a videogame,a specific application unrelated to a videogame, or the user's operatingsystem environment including some or all applications the user hasexecuted. Multiple Game Signals 220 and User Signals 210 may also becombined to create the Game Signal 220 or User Signal 210.

In the embodiment shown, the Server Infrastructure 100 responds torequests from the Local Broadcast Software 240 executing on the LocalComputer 230, and further retrieves the Overlay Configuration 110 asneeded. The Local Software may be stored on a non-volatile informationmedium, or it may be downloaded onto the Local Computer 230 via, e.g.,the Internet 120.

The core functionalities of the Server Infrastructure 100 include, butare not limited to:

1. Responding to requests from the Local Broadcast Software 240, LocalComputer 230 or Streaming Service API 130;

2. Hosting a web page that allows users to edit their OverlayConfiguration 110;

3. Executing the API Data Collector 260, which may perform, but is notlimited to, the following actions:

-   -   a. Maintains persistent connections with the Streaming Service        API(s) 230;    -   b. Receives data from Alternative API Data Sources 270;    -   c. Stores metadata about the data received from the Streaming        Service API(s) 230 and Alternative API Data Sources 270;    -   d. Stores data aggregated from one or more source related to the        user in the user's account;

4. Generating the Graphical Overlay 200 based on the user's OverlayConfiguration 110 at set intervals, based on specific data events asthey are received in real time by the API Data Collector 260, uponrequest, or otherwise as needed;

5. Maintaining user account information;

6. Hosting the Multistream Service 250; and

7. Hosting and web sites required to support the disclosed system.

The core functionalities of the Local Broadcast Software 240 include,but are not limited to:

1. Receiving a Game Signal 220 and, optionally, a User Signal 210 fromthe Local Computer 230;

2. Using the Internet 120 to retrieve the Graphical Overlay 200 from theServer Infrastructure 100;

3. Using the Video Encoder 190 to produce a video file from the GameSignal 220, the optional User Signal 210, and the Graphical Overlay 200;

4. Sending authentication information to the Streaming Service 150 toidentify the user uploading the video file;

5. Uploading the video file to a Multistream Service 250 using StreamingProtocols 180;

6. Storing user settings related to, but not limited to:

-   -   a. Streaming Services 150 the user may broadcast their encoded        video file;    -   b. Encoding settings used to configure and optimize the Video        Encoder 190; and    -   c. Streaming settings used to configure and optimize the        Streaming Protocols 180 used to upload the video file to        Streaming Service 150.

The core functionalities of the Multistream Service 250 include, but arenot limited to:

1. Storing user configuration settings to control which StreamingService(s) 150 an uploaded video file should be redistributed to;

2. Optionally receiving authentication information from the LocalBroadcast Software 240;

3. If authentication information is received, forwarding saidauthentication information to one or more Streaming Services 150;

4. Receiving the uploaded video file from the Local Broadcast Service240 via a Streaming Protocol 180;

5. Optionally decoding the video file, then re-encoding the file tooptimize it for individual Streaming Service(s) 150; or

6. Uploading the video file to one or more Streaming Service 150 using aStreaming Protocol 180.

The core functionalities of each of the Streaming Service(s) 150include, but are not limited to:

1. Storing account details for the user;

2. Receiving authentication information from the Local BroadcastSoftware 240 and/or the Multistream Service 250;

3. Using the authentication information to identify the user uploadingthe video file;

4. Receiving the uploaded video file from the Multistream Service 250via a Streaming Protocol 180;

5. Decoding the video file;

6. Playing the decoded video file for Viewers 170 to consume on theuser's channel;

7. Gathering metadata about Viewer Interactions 160 including, but notlimited to:

-   -   a. The type of interaction;    -   b. The time of the interaction.    -   c. The Viewer's 170 account details; and

8. Storing Viewer Interactions 160 for retrieval by the StreamingService API(s) 140.

The core functionalities of the Streaming Service API(s) 130 include,but are not limited to:

1. Retrieving Viewer Interactions 160 for processing;

2. Processing Viewer Interactions 160 into Stream Events 140 formattedfor use in the Streaming Service API(s) 130;

3. Sending the Stream Events 140 to the API Data Collector 260 via theStreaming Service API(s) 130.

The primary implementations of the Alternative API Data Sources 270include but are not limited to:

1. Data received directly from the videogame;

2. Data received from a computer vision and/or an artificialintelligence engine analysis of the game;

3. Data received from third-party APIs related to the user's game, theuser, or the Viewers 170.

Configuring an Overlay

FIG. 2 shows an illustrative process view of a user configuring theirGraphical Overlay 200.

A User 350 launches the Local Software 280. The Local Software 280 maybe executed by any type of a Local Computer 230, and it may be presentedas a web page or a local application. The User 350 then uses the LocalSoftware 280 to authenticate with the Server Infrastructure 100.Credentials are then passed from the Local Software 280 to the ServerInfrastructure 100, which validates the authentication attempt.

Once authenticated, the User 350 then uses the Local Software 280 tocreate a new Graphical Overlay 200, which saves a new copy of theOverlay Configuration 110 in the Server Infrastructure 100. The User 350then selects Images 300 or a Templates 290 to add the Graphical Overlay200. The User 350 then has the option to edit the Image 300 or Template290, which updates the Overlay Configuration 110 in their account.

In some embodiments, the User 350 then associates the Image 300 orTemplate 290 with specific real-time event(s). In another embodiment,the User 350 then associates the Image 300 or Template 290 withtimer(s). In another embodiment, the User 350 has already associated theImage 300 or Template 290 with specific real-time event(s), so the User350 either verifies or modifies the existing associations. In yetanother embodiment, the User 350 associates different real-time event(s)from different Streaming Services 150 with different Images 300 orTemplates 290, which are then saved to Overlay Configuration(s) 110 thatcorrespond to one or more Streaming Service 150. Once the User 350 makesany of the aforementioned modifications, the Overlay Configurations 110is updated in their account.

The User 350 determines whether the Graphical Overlay 200 is complete.If not, the User 350 repeats the process of adding Images 300 orTemplates 290 to the Graphical Overlay 200. If so, the final OverlayConfiguration 110 is saved to the user's account for later retrieval.

Graphical Overlay

FIG. 3 is a non-limiting example of a configured graphical overlayaccording to some embodiments. In some embodiments, Images 300 andTemplates 290 within the Graphical Overlay 200 are configured to appearwhen the Streaming Service API(s) 130 report specific events including.The notifications can include, but are not limited to:

1. A Viewer 170 has followed the User 350, meaning they will receivenotifications from the Streaming Service when the User's 350 broadcastis active.

2. A Viewer 170 has subscribed to the User's 350 channel. When a Viewer170 subscribes to a streamer's channel, they pay a monthly subscriptionfee in exchange for subscriber-only privileges, such as access tosubscriber-only interactions with the User 350 and their channel oraccess to the User's 350 private chat servers or newsletters. Thebenefits are configured by the User 350, therefore are not limited tonor required to include the aforementioned benefits.

3. A Viewer 170 has donated money to the User 350. While StreamingServices 150 provide the infrastructure for Viewers 170 to subscribe orfollow the User 350, monetary donations are usually facilitated bythird-party services, such as Streamlabs.

In the non-limiting example illustrated in FIG. 3, a FollowerNotification 390 comprises a predetermined animation and text conveyingthat a Viewer 170, in this case “whitewalkerzzzz”, has followed the User350. The Donation Notification 400 also comprises a predeterminedanimation and text conveying that a Viewer 170, in this case “John”, hasdonated, in this case, $95 to the User 350. The SubscriptionNotification 410 also comprises a predetermined animation and textconveying that a Viewer 170, in this case “gitthezambiescorrrl”, hassubscribed to the User's 350 channel.

The aforementioned are non-limiting examples of Images 300 being writtento a Graphical Overlay 200 image file in response to specific StreamingService API 130 data points. Said Graphical Overlay 200 image file willbe subsequently retrieved by the User's 350 Local Broadcast Software240, where, per the example provided in FIG. 1A, FIG. 1B, and FIG. 2. Itwill be combined with the Game Signal 220 and optionally the User Signal210 by the Video Encoder 190 to produce an encoded video file. In thenon-limiting example illustrated in FIG. 3, the black backgroundrepresents a transparent layer, and the Graphical Overlay 200 willappear as if it is “on top” of the video signals provided by the GameSignal 220 and the User Signal 210.

In some embodiments, one or more of the aforementioned examples mightinclude text without an associated Image 300. In other embodiments, oneor more of the aforementioned examples might include an Image 300without text. In other embodiments, one or more Overlay Configuration110 might correspond to one or more specific Streaming Service 150.Furthermore, while editing the Graphical Overlay 200 the User 350 mayassign the position at which each notification appears. In someembodiments, the program automatically recommends the position for theUser 350, which the User 350 can adjust. The User 350 may also changethe font the font colors, the animation included, the duration,transitions, and a wide range of additional configuration options topersonalize their Graphical Overlay 200.

Connecting Streaming Services to the User's Account

FIG. 4 shows an illustrative process view of a user connecting theiraccount to one or more streaming services.

A User 350 launches the Local Software 280. The Local Software 280 maybe executed by any type of a Local Computer 230, and it may be presentedas a web page or a local application. The User 350 then uses the LocalSoftware 280 to authenticate with the Server Infrastructure 100.Credentials are then passed from the Local Software 280 to the ServerInfrastructure 100, which validates the authentication attempt.

Once authenticated, the User 350 chooses to establish a new connectionto a Streaming Service 150 using the Local Software 280. The ServerInfrastructure 100 provides an interface for connecting the newStreaming Service. Credentials are then passed from the User 350 to thethird-party Streaming Service 150 via the Server Infrastructure 100.Once authenticated, the Server Infrastructure 100 stores and associatesthe Streaming Service Connection 430 with the User's 350 account withinthe Server Infrastructure 100.

After the Streaming Service Connection 430 has been saved, the User 350decides whether they are finished connecting Streaming Services 150 totheir account. If not, they repeat the process of connecting a newStreaming Service 150 to their account. Otherwise, the process iscomplete.

First Illustrative Embodiment

FIGS. 5A and 5B shows a beginning-to-end illustrative process view ofthe disclosed methods, wherein the streaming architecture uses aMultistream Service 250 and the Graphical Overlay 200 is encoded by theLocal Broadcast Software 240.

A User 350 launches the Local Software 280. The Local Software 280 maybe executed by any type of a Local Computer 230, and it may be presentedas a web page or a local application. The User 350 then uses the LocalSoftware 280 to authenticate with the Server Infrastructure 100.Credentials are then passed from the Local Software 280 to the ServerInfrastructure 100, which validates the authentication attempt.

Once authenticated, the User 350 uses the Local Software 280 to connectone or more Streaming Service 150 to the Server Infrastructure 100. TheStreaming Service 150 connection(s) are then stored in the User's 350account for later access via the Multistream Service 250.

The User 350 then launches the Local Broadcast Software 240. The User350 uses the Local Broadcast Software to authenticate with the ServerInfrastructure 100. Credentials are then passed from the Local BroadcastSoftware 240 to the Server Infrastructure 100, which validates theauthentication attempt.

Once authenticated, the User 350 initiates connection(s) with theStreaming Service(s) 150. The User's 350 credentials or API tokens arepassed to the Streaming Server(s) 380 via the Multistream Service 250,and the Streaming Server(s) 380 return an active connection to theMultistream Service 250. Once the connection(s) are returned, the ServerInfrastructure 100 initiates the API Data Collector 260, which initiatesand maintains connections with the Streaming Service API(s) 130. The APIData Collector 260 then begins reading data related to the User's 350channel(s) for each of the Streaming Service(s) 150 to which the User350 has active connections. The Streaming Service API(s) 130 then rejectthe API Data Collector's 260 connection attempts or confirm that theconnection(s) are valid. If the connections are rejected, the API DataCollector 260 attempts to initiate the connection to the StreamingService API(s) 130 again. If the connections are valid, the API DataCollector 260 begins receiving real-time data events from the StreamingService API(s) 130.

The Server Infrastructure 100 then retrieves the User's 350 OverlayConfiguration 110, which contains one or more Image(s) 300 orTemplate(s) 290. The Server Infrastructure 100 then uses the OverlayConfiguration 110 and data from the API Data Collector 260 to begingenerating the Graphical Overlay 200 image file. Variations in thegenerated Graphical Overlay 200 typically consist of animations, Images300 or Templates 290 that are configured to appear when the ServerInfrastructure receives specific data events from the API Data Collector260. Variations can also consist of Images 300 that remain static untilmanually changed by the User 350. The Graphical Overlay 200 is thengenerated at regular intervals for as long as the User's 350 streamingsession is active.

The Local Broadcast Software 240 then collects the user's Game Signal220. User Signal 210, and retrieves the generated Graphical Overlay 200from the Server Infrastructure 100. The sources are then encoded by theVideo Encoder 190 and uploaded to the Multistream Service 250 using aStreaming Protocol 180, including but not limited to HLS, FLV, RTMP,RTSP, and DASH. The Multistream Service 250 then uploads the file usinga Streaming Protocol 180 to each of the active Streaming ServiceConnections 430 in the User's 350 account. Once uploaded to each of theStreaming Service(s) 150, the encoded video file is decoded and playedfor Viewers 170 to consume.

In other embodiments, the Multistream Service 250 decodes the videofile, then uses a Video Encoder 190 to re-encode a copy of the videofile in a manner that is optimized for each of the Streaming Service(s)150 prior to uploading it to the Streaming Service(s) 150 using aStreaming Protocol 180.

As Viewers 270 interact with the User's 350 channel(s) on the variousStreaming Service(s). the Streaming Service API(s) 130 record theinteractions and convert them into a data format that can be easilyshared with the API Data Collector 260. Interactions include but are notlimited to: chat subscriptions, follows, donations, minigames, andmiscellaneous purchases.

In some embodiments, Alternative API Data Sources 270, data from sourcesother than the Streaming Service API(s) 130, may send data to the APIData Collector 260 for use in creating Graphical Overlays 200.

The aforementioned process of encoding the sources to playback repealsuntil the User 350 decides to stop the broadcast. When the broadcast isstopped, the Local Broadcast Software 240 stops generating and uploadingthe encoded video file; it then sends a signal to end the broadcast, theServer Infrastructure 100 stops generating the Graphical Overlay 200,the Multistream Service 250 stops operation and notifies the StreamingService(s) 150 to mark the User's 350 stream(s) as inactive, theStreaming Service API(s) 130 stop generating data based on Viewer 170actions, and the API Data Collector 260 stops receiving data.

Second Illustrative Embodiment

FIGS. 6A and 6B shows a beginning-to-end illustrative process view ofthe disclosed methods, wherein the streaming architecture uses aMultistream Service 250 and one or more Graphical Overlays 200 are addedand encoded by the Multistream Service 250, which uploads a copy of thevideo to the Streaming Services 150 corresponding to each copy of theGraphical Overlay 200.

A User 350 launches the Local Software 280. The Local Software 280 maybe executed by any type of a Local Computer 230, and it may be presentedas a web page or a local application. The User 350 then uses the LocalSoftware 280 to authenticate with the Server Infrastructure 100.Credentials are then passed from the Local Software 280 to the ServerInfrastructure 100, which validates the authentication attempt.

Once authenticated, the User 350 uses the Local Software 280 to connectone or more Streaming Service 150 to the Server infrastructure 100. TheStreaming Service 150 connection(s) are then stored in the User's 350account for later access via the Multistream Service 250.

The User 350 then launches the Local Broadcast Software 240. The User350 uses the Local Broadcast Software to authenticate with the ServerInfrastructure 100. Credentials are then passed from the Local BroadcastSoftware 240 to the Server Infrastructure 100, which validates theauthentication attempt.

Once authenticated, the User 350 initiates connection(s) with theStreaming Service(s) 150. The User's 350 credentials or API tokens arepassed to the Streaming Server(s) 380 via the Multistream Service 250,and the Streaming Server(s) 380 return an active connection to theMultistream Service 250. Once the connection(s) are returned, the ServerInfrastructure 100 initiates the API Data Collector 260, which initiatesand maintains connections with the Streaming Service API(s) 130. The APIData Collector 260 then begins reading data related to the User's 350channel(s) for each of the Streaming Service(s) 150 to which the User350 has active connections. The Streaming Service API(s) 130 then rejectthe API Data Collectors 260 connection attempts or confirm that theconnection(s) are valid. If the connections are rejected, the API DataCollector 260 attempts to initiate the connection to the StreamingService API(s) 130 again. If the connections are valid, the API DataCollector 260 begins receiving real-time data events from the StreamingService API(s) 130.

The Server Infrastructure 100 then retrieves the User's 350 OverlayConfiguration(s) 110, which contains one or more Image(s) 300 orTemplate(s) 290 and correspond to one or more Streaming Service(s) 150.The Server Infrastructure 100 uses the Overlay Configuration(s) 110 anddata from the API Data Collector 260 specific to each Streaming Service150 to begin generating one or more Graphical Overlay 200 image file(s)based on data received from and corresponding to each of the StreamingService(s) 150. The result is a Graphical Overlay 200 that containsImages 300 generated in response to data specifically related to theassociated Streaming Service 150, as opposed to a one Graphical Overlay200 that generates images based on data received from all of theStreaming Services 150.

Variations in the generated Graphical Overlay 200 typically consist ofanimations, Images 300 or Templates 290 that are configured to appearwhen the Server Infrastructure receives specific data events from theAPI Data Collector 260. Variations can also consist of Images 300 thatremain static until manually changed by the User 350. The GraphicalOverlay 200 is then generated at regular intervals for as long as theUser's 350 streaming session is active.

The Local Broadcast Software 240 then collects the user's Game Signal220 and User Signal 210. The sources are then encoded by the VideoEncoder 190 and uploaded to the Multistream Service 250 using aStreaming Protocol 180, including but not limited to HLS, FLV, RTMP,RTSP, and DASH. The Multistream Service 250 then retrieves the GraphicalOverlay 200 image file(s), decodes the encoded stream for the videofile, makes one copy of the decoded video file for each GraphicalOverlay 200 image file, and re-encodes (i.e. transcodes) the originalvideo file to include the Graphical Overlay 200 image file. TheMultistream Service 250 uploads each video file using a StreamingProtocol 180 to each of the active and corresponding Streaming ServiceConnections 430 in the User's 350 account. Once uploaded to each of theStreaming Service(s) 150, the encoded video file is decoded and playedfor Viewers 170 to consume.

In other embodiments, the Multistream Service 250 decodes the videofile, duplicates the video file, inserts the Graphical Overlay 200 imagefile, then uses a Video Encoder 190 to re-encode a copy of the videofile in a manner that is optimized for each of the Streaming Service(s)150 prior to uploading it to the Streaming Service(s) 150 using aStreaming Protocol 180.

In other embodiments, the Multistream Service 250 duplicates the videofile prior to decoding.

In other embodiments, the Multistream Service 250 optimizes the videofile based on meta-data related to the video file.

As Viewers 270 interact with the User's 350 channel(s) on the variousStreaming Service(s), the Streaming Service API(s) 130 record theinteractions and convert them into a data format that can be easilyshared with the API Data Collector 260. Interactions include but are notlimited to: chat, subscriptions, follows, donations, minigames, andmiscellaneous purchases.

In some embodiments, Alternative API Data Sources 270, data from sourcesother than the Streaming Service API(s) 130, may send data to the APIData Collector 260 for use in creating Graphical Overlays 200.

The aforementioned process of encoding the sources to playback repeatsuntil the User 350 decides to stop the broadcast. When the broadcast isstopped, the Local Broadcast Software 240 stops generating and uploadingthe encoded video file; it then sends a signal to end the broadcast, theServer Infrastructure 100 stops generating the Graphical Overlay 200 theMultistream Service 250 stops operation and notifies the StreamingService(s) 150 to mark the User's 350 stream(s) as inactive, theStreaming Service API(s) 130 stop generating data based on Viewer 170actions, and the API Data Collector 260 stops receiving data.

1-20. (canceled)
 21. A system comprising: one or more processors; andone or more machine-readable, non-transitory storage mediums thatinclude instructions configured to cause the one or more processors to:establish communication with a first streaming service and a secondstreaming service configured to receive and transmit information;receive video content defined by an image and/or audio contentassociated with a user; stream a first copy of the video content to thefirst streaming service; stream a second copy of the video content tothe second streaming service; receive a first set of viewer inputinformation associated with a first user's interaction with the firststreaming service; and based on the first set of viewer inputinformation, selectively apply a first graphical or audio overlay to thefirst copy of the video content.
 22. The system of claim 21 wherein thefirst graphical or audio overlay is not applied to the second copy ofthe video content.
 23. The system of claim 21 wherein the one or moremachine-readable, non-transitory storage mediums further includeinstructions configured to cause the one or more processors to: receivea second set of viewer input information associated with a second user'sinteraction with the second streaming service; and based on the secondset of viewer input information, selectively apply a second graphical oraudio overlay to the second copy of the video content.
 24. The system ofclaim 21 wherein the graphical or audio overlay is encoded by a localbroadcast software then sent to a multistream service.
 25. The system ofclaim 21 wherein the graphical or audio overlay is added to the videoafter it is received by a multistream service.
 26. The system of claim21 wherein the video content is received from a client computingplatform.
 27. The system of claim 21 wherein the first set of viewerinput information is received from a client computing platform.
 28. Amethod comprising: establishing communication with a first streamingservice and a second streaming service configured to receive andtransmit information; receiving video content defined by an image and/oraudio content captured from the client computing platform associatedwith a user; streaming a first copy of the video content to the firststreaming service; streaming a second copy of the video content to thesecond streaming service; receiving a first set of viewer inputinformation associated with a first user's interaction with the firststreaming service; and based on the first set of viewer inputinformation, selectively applying a first video or audio overlay to thefirst copy of the video content.
 29. The method of claim 28 wherein thefirst video or audio overlay is not applied to the second copy of thevideo content.
 30. The method of claim 28 further comprising: receiving,from the second streaming service, a second set of viewer inputinformation associated with a second user's interaction with the secondstreaming service; and based on the second set of viewer inputinformation, selectively applying a second audio overlay to the secondcopy of the video content.
 31. The method of claim 30 wherein the secondvideo or audio overlay is different than the first video or audiooverlay.
 32. The method of claim 30 wherein the second video or audiooverlay is not applied to the first copy of the video content.
 33. Themethod of claim 28 wherein the method is performed by software operatingon the client computing platform, and wherein the first and secondstreaming services are operated by one or more servers in electroniccommunication with the client computing platform.
 34. The method ofclaim 28 wherein the selectively applied first video or audio overlay tothe first copy of the video content is executed in real-time as definedby the first set of viewer input information.
 35. A non-transitorycomputer-program product tangibly embodied in a machine-readablenon-transitory storage medium that includes instructions configured tocause one or more processors to: establish communication with a firststreaming service and a second streaming service configured to receiveand transmit information; receive video content defined by an imageand/or audio content captured from a client computing platformassociated with a user; stream a first copy of the video content to thefirst streaming service; stream a second copy of the video content tothe second streaming service; receive a first set of viewer inputinformation associated with a first user's interaction with the firststreaming service; and based on the first set of viewer inputinformation, selectively apply a first video or audio overlay to thefirst copy of the video content.
 36. The computer-program product ofclaim 35 wherein the first video or audio overlay is not applied to thesecond copy of the video content.
 37. The computer-program product ofclaim 35 wherein the machine-readable, non-transitory storage mediumfurther includes instructions configured to cause the one or moreprocessors to: receive a second set of viewer input informationassociated with a second user's interaction with the second streamingservice; and based on the second set of viewer input information,selectively apply a second video or audio overlay to the second copy ofthe video content.
 38. The computer-program product of claim 37 whereinthe second video or audio overlay is different than the first video oraudio overlay.
 39. The computer-program product of claim 37 wherein thesecond video or audio overlay is not applied to the first copy of thevideo content.
 40. The computer-program product of claim 35 wherein theinstructions are executed by software operating on the client computingplatform, and wherein the first and second streaming services areoperated by one or more servers in electronic communication with theclient computing platform.